Skip to content

Conversation

@mahlonduke
Copy link

No description provided.


These are not run from the end user's deployment, and hence do not need to be authorized by the user, so authorization
and accessing a token is are combined into one step for these application.
Service applications are not run on behalf of a user, so they're great for situations where you need to access and move data, but don't need to attribute the action to an individual. Authorization and accessing a token are combined into one step for these applications.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[I] This appears to be misleading – a service application is run on behalf of the end-user, with the permissions of the user who created it.

  • Clarify wording

## Web Applications

Web applications require the end-user to authorize an application before it can make any requests. Hence token
Web applications are run on behalf of a user, so they're great for situations where you need to take an action, and attribute the action to an individual. To authorize a web application, the user must first authorize the application, so token
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[I] This appears to be misleading – a web application is run as the end-user (with their permissions), not on behalf of them.

  • Clarify wording

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants